Is it possible to perform a trace analysis on an object and then an impact analysis on the objects turned up by the trace analysis? For example, object A has child links to objects B and C (in a separate module). Objects B and C then have parent links to objects D and E (in a separate module). I'd like to display information about objects B, C, D and E in the module for object A. The parent links from B and C that I'm interested in are in separate link modules from those that link to A so I'm not creating any circular references. Thanks for any insight.
SystemAdmin - Tue Feb 01 18:58:11 EST 2011 |
|
Re: First trace then impact analysis?
SystemAdmin - Tue Feb 01 19:43:37 EST 2011
Assuming that all of your links between the objects all flow in one direction, then this sounds like a job for the DOORS Analysis Wizard. Select Analysis > Wizard from the module menu. This wizard enables you to insert columns that shows you what is the other end of links and can be made to recurse and show information for objects that are more than one link depth away. It doesn't matter that you have links in different link modules, the Analysis Wizard has options for links going through any link module or specific link modules. Have a play around with it as there are many options.
To get a more graphical idea of the impact of a change - have a look at the Traceability Explorer, select Analysis > Traceability Explorer. This can provide you with an expandable display of the tree of linked outgoing or incoming objects. The Traceability Explorer might seem a little clunky but take some time to play around with the options under it's View menu as I have found it be a useful aid for impact assessment. You can navigate to objects that it displays via a RH mouse click so that you can investigate further. As a tip though, use filtering in the module to only show objects of interest as the Traceability Explorer stays in synch with whatever is visible in the current module - this helps to focus on the important stuff and get rid of the clutter.
Paul Miller
Melbourne, Australia
|
|
Re: First trace then impact analysis?
SystemAdmin - Wed Feb 02 18:13:30 EST 2011 SystemAdmin - Tue Feb 01 19:43:37 EST 2011
Assuming that all of your links between the objects all flow in one direction, then this sounds like a job for the DOORS Analysis Wizard. Select Analysis > Wizard from the module menu. This wizard enables you to insert columns that shows you what is the other end of links and can be made to recurse and show information for objects that are more than one link depth away. It doesn't matter that you have links in different link modules, the Analysis Wizard has options for links going through any link module or specific link modules. Have a play around with it as there are many options.
To get a more graphical idea of the impact of a change - have a look at the Traceability Explorer, select Analysis > Traceability Explorer. This can provide you with an expandable display of the tree of linked outgoing or incoming objects. The Traceability Explorer might seem a little clunky but take some time to play around with the options under it's View menu as I have found it be a useful aid for impact assessment. You can navigate to objects that it displays via a RH mouse click so that you can investigate further. As a tip though, use filtering in the module to only show objects of interest as the Traceability Explorer stays in synch with whatever is visible in the current module - this helps to focus on the important stuff and get rid of the clutter.
Paul Miller
Melbourne, Australia
Unfortunately the links go in both directions. In my example the links from B/C to D/E are in the opposite direction as the links from A to B/C. I tried to use the Wizard but as you stated it looks like the links need to be in the same direction.
If anyone has any tips on displaying information from links that go one-level-deep and then one-level-up from the one-level-deep module, that is what I'm looking for. I realize it is a bit of a strange operation to want to execute but the path is really determined by the link modules, not the link direction.
Thanks again.
|
|
Re: First trace then impact analysis?
SystemAdmin - Wed Feb 02 19:20:46 EST 2011 SystemAdmin - Wed Feb 02 18:13:30 EST 2011
Thanks for the reply Paul.
Unfortunately the links go in both directions. In my example the links from B/C to D/E are in the opposite direction as the links from A to B/C. I tried to use the Wizard but as you stated it looks like the links need to be in the same direction.
If anyone has any tips on displaying information from links that go one-level-deep and then one-level-up from the one-level-deep module, that is what I'm looking for. I realize it is a bit of a strange operation to want to execute but the path is really determined by the link modules, not the link direction.
Thanks again.
http://publib.boulder.ibm.com/infocenter/ieduasst/rtnv1r0/index.jsp?topic=/com.ibm.iea.doors/plugin_coverpage.html
This will only get you to a Home page for DOORS tutorials - Under the "Rational DOORS" heading in the right hand pane, look for "V9.2" and select the link below this named "Usability" - look for a tutorial named "Showing traceability for different directions".
Paul Miller
Melbourne, Australia
|
|
Re: First trace then impact analysis?
llandale - Thu Feb 03 15:45:36 EST 2011 SystemAdmin - Wed Feb 02 19:20:46 EST 2011
IBM has a workaround using a combination of the Analysis Wizard and DXL Attributes to cater for when links are not going in the same direction - you might find that it satisfies your needs - the following URL will take you to an IBM tutorial presentation on this workaround.
http://publib.boulder.ibm.com/infocenter/ieduasst/rtnv1r0/index.jsp?topic=/com.ibm.iea.doors/plugin_coverpage.html
This will only get you to a Home page for DOORS tutorials - Under the "Rational DOORS" heading in the right hand pane, look for "V9.2" and select the link below this named "Usability" - look for a tutorial named "Showing traceability for different directions".
Paul Miller
Melbourne, Australia
Fine. Except that it doesn't handle duplicate entries very well; such as A1<-B1->C1 and A1<-B2->C1; you would prefer to see C1 displayed once but it will get displayed twice. I suppose though that you cold parse the attrDXL value and store each reference to a C object separately.
|
|